Method And System For Efficiently Routing Messages

ABSTRACT

Efficient routing of a message over a data network. A first communication device sends a message to a telemetry gateway or short message arbitrator. The telemetry gateway or short message arbitrator determines the communication protocol of the first communication device and the communication protocol of a second communication device. The telemetry gateway or short message arbitrator converts the message to a data format compatible with the second communication device, wherein the message is converted to one of at least three different communication protocols. The telemetry gateway or short message arbitrator then forwards the message for receipt by the second communication device. The telemetry gateway or short message arbitrator can convert and forward the message without completing a store and forward process.

RELATED PATENT APPLICATION

This patent application claims priority to and is a continuation of thepatent application entitled “Telemetry Gateway,” filed on Jun. 12, 2007and assigned U.S. Nonprovisional patent application Ser. No. 11/811,855,which is a continuation of the patent application entitled “Method andSystem for Improved Short Message Services,” filed on Jul. 6, 2004,assigned U.S. patent application Ser. No. 10/885,445, and issued as U.S.Pat. No. 7,245,928, which is a continuation-in-part of the patentapplication entitled “Interconnect System and Method for MultipleProtocol Short Message Services,” filed on Oct. 27, 2000, assigned U.S.patent application Ser. No. 09/699,312, and issued as U.S. Pat. No.6,856,808. Applicants hereby incorporate by reference herein the fulldisclosure of U.S. application Ser. No. 11/811,855 and U.S. Pat. Nos.7,245,928 and 6,856,808.

FIELD OF THE INVENTION

The present invention relates to the exchange of short messages betweena telemetry gateway and a remote location, and more particularly toeliminating delays associated with communicating short messages throughconventional short message center platforms.

BACKGROUND OF THE INVENTION

Short Message Service (SMS) is an inherent capability of most digitalwireless telecommunications systems. The radio technologies associatedwith each of the digital wireless telecommunications systems aretechnically incompatible at the radio signal layer, but most arecompatible at the intersystem SS7 transport layer. Currently, thediffering RF technologies, e.g., time division multiple access (TDMA),code division multiple access (CDMA), and global system for mobiletelecommunications (GSM), have at least partial technical compatibilityover the telephone industry's SS7 inter-networking system. The partialcompatibility of these RF technologies is possible because the basictransport format is specified in the SS7 standard; however, many of themessaging details are implementation specific.

Even though it is possible for current short message service centerplatforms (SMSC) to support all of these multiple protocols, typically,an installed SMSC only supports the protocol of the cellulartelecommunication system into which it is installed. For example, if theSMSC is installed into an IS136 type TDMA system, the SMSC supports onlythe TDMA protocol. Similarly, if the SMSC is installed into a GSMsystem, then the SMSC supports only the GSM protocol. In other words,although most current SMSC's can interface with any of the currentlypopular digital cellular systems, the SMSC's do so on an individualbasis, not all simultaneously.

For example, in one network, the nodes communicate using different dataformatting standards, such as integrated services digital network (ISDN)and the Japanese X.50 standard. Each of the nodes is connected to aformat converter. The format converter acts as a bi-directionalconverter for converting between two data formats and thus allowscommunication between the two nodes.

The format converter reformats the data formatted in the X.50 standardinto the ISDN format. The format converter accomplishes the conversionby storing the incoming X.50 data in an aligned data RAM with offsets,to provide an appropriate alignment among the frames of the data. Then,a format conversion module reformats the data into the ISDN format onebyte at a time.

In another network, a subscriber in an electronic messaging network canaccess messages in a variety of formats. A subscriber may receivemessages through a variety of types of equipment, such as a voice mailsystem, an e-mail system, a facsimile machine and a telephone, allconnected to a wireline network. The subscriber may access thesemessages through a pager, a cellular telephone, or a personal digitalassistant, each connected to a different wireless network. Thesubscriber selects the wireline or wireless network and media format tobe used for delivering messages or notifying a subscriber that a messagehas been received.

For example, the subscriber may elect to have notification of a voicemail or facsimile receipt directed to the personal digital assistant(PDA) in the form of an e-mail message. In accordance with the method ofthe network, the subscriber's selection is implemented through thepersonal intercommunications inter-networking system, which performs theappropriate data conversion from one protocol to another and deliversthe e-mail message.

In yet another network, an intelligent signaling transfer point (ISTP)is included in a telephone network with a database for storing callprocessing control information. Calls from one station on the network toanother are either passed through or intercepted at the ISTP andscreened in accordance with criteria stored in the database, such astime of day, a certain originating area or caller, or a specified callcount value.

In still another network, a data collection device is provided for usewith any one of the following: TDMA; CDMA; frequency division multipleaccess (FDMA); GSM; and personal access communications systems (PACS)technologies. But, the data collection device does not use multiple suchtechnologies in a single system. These systems and methods only teachconversion between two specific formats.

A further limitation with conventional SMS systems is that the SMS datatransmissions are handled by the SMSC. The SMSCs use the addressinformation contained within the data transmission to communicate withHome Location Registers (“HLRs”) and route the data to the correctrecipient. The SMS text messages can originate and terminate at cellularmobile radiotelephones or at other external messaging entities coupledto the cellular network such as email, voicemail, and web-basedmessaging systems.

SMS data transmissions are routed from the SMSC to the recipient via oneor more switches. Once an SMS data packet arrives at the receivingdevice, the message is extracted from its packet and formatted fordelivery. For example, if the receiving unit is a cellular mobileradiotelephone, the unit formats the message for display on the unit'sdisplay screen. Alternatively, if the receiving unit is an externalmessaging system, an SMSC can format the message for transmission withinan email message for delivery to a user external to the cellulartelephone system.

The SMSCs are deployed by cellular carriers and serve the customerswithin the carrier's private network. For example, FIGS. 5 and 6illustrate conventional SMS systems 500 and 600 using SMSCs operated bya local and regional carrier, respectively. In each of the conventionalsystems illustrated in FIGS. 5 and 6, the SMSCs 525 and 625 receive andstore messages from radios 505 and 605. The SMSCs determine thedestinations for the messages through a set of queries. Once there isavailable bandwith, the SMSC can deliver the messages to the appropriatedestination. SMSCs 525 and 625 can also receive messages from externalsystems, such as an email system, that are destined for radios 505 and605. The SMSCs 525 and 625 query the HLRs 520 and 620 to determine thelocations of the destination radios 505 and 605. Once there is availablebandwith, the SMSCs 525 and 625 can deliver the messages to radios 505and 605. Significantly, all messages transmitted within each of systems500 and 600 must use the same communication protocol. Conventional SMSCs525 and 625 generally are not equipped to convert messages havingdifferent communication protocols.

FIGS. 7 and 8 illustrate conventional systems 700 and 800 forcommunicating roaming messages between different networks. FIG. 7illustrates a home SMSC 730 coupled to HLR 735 that transmits messagesto and receives messages from switch 715. FIG. 8 illustrates system 800where a local SMSC 825 and an SMS clearinghouse 830 are used tocommunicate with a home SMSC 835. In each of systems 700 and 800, theswitch or the SMSCs send a set of queries to the destination network inorder to transmit messages. Furthermore, although the roaming messagesare transmitted between different networks, the format of the messagesis the same.

The SMSC of the conventional networks illustrated in FIGS. 5, 6, 7, and8 acts as a “store and forward” system for the SMS data transmissions.The SMSC determines the routing for the data transmission and places thedata in a queue for delivery to a cellular mobile radiotelephone orother messaging device. One shortcoming of conventional SMS systems isthe delay in delivering the data transmissions queued at the SMSC.Typical delays for delivering messages can last minutes or hours.

One of the causes for the delay is that SMS messages are often assigneda lower delivery priority as compared to data transmissions containingvoice communications. The low priority assigned to SMS messages storedin a queue at the SMSC causes a delay in their delivery. This delay isparticularly noticeable when a carrier lacks sufficient bandwidth on itsnetwork. A further cause for delay are the inefficient steps an SMSCtakes to route and deliver a data transmission. For example, the SMSCqueries the HLR each time it is delivering a message to a mobilecommunication device. The HLR is a database of profiles for subscriberscomprising account and service information.

Accordingly, there is a need in the art for a system that canefficiently route SMS messages from originators to recipients.Specifically, there is a need in the art to communicate more efficientlywith serving switches and avoid the delays caused by an SMSC. Acommunication platform is needed that delivers messages promptly insteadof storing them for later delivery when there is available bandwidth.The needed communication platform should also eliminate unnecessarysteps as part of the communication process. There is a further need fora communication platform that can communicate with remote stations thatuse different digital cellular or personal communication formats.

SUMMARY OF THE INVENTION

The method and system disclosed herein is capable of efficiently routingmessages without the delay typically associated with conventionaltechnology. In an exemplary embodiment, a telemetry gateway can performcertain functions of conventional SMS systems to support the delivery ofcommunications from incompatible networks. The telemetry gateway maycommunicate over a SS7 inter-networking system. It further may convertand forward messages without performing a store and forward process asrequired by conventional technology.

In an exemplary embodiment, a telemetry gateway can receive a messagefrom a radio communication device; convert the message from one ofseveral standard messaging protocols to a protocol compatible with asecond communication device, such as a message service provider; andtransmit the message to the second communication device. Thistransmission can be performed by the telemetry gateway without the storeand forward delay associated with conventional technology.

In another exemplary embodiment, the telemetry gateway may receive amessage from a communication device, such as a service provider; query aMSC for routing information for the message; convert the message to oneof at least three different formats; and transmit the message to the MSCfor delivery to a recipient without the use of a store and forwardprocess. The recipient may be a radio communication device or othermobile device.

In a further exemplary embodiment, a short message arbitrator mayprovide efficient and rapid delivery of a short message. The shortmessage arbitrator can receive a message from a first device fordelivery to a second device; access a database containing a profile forthe first device and the second device; analyze whether the first deviceand the second device communicate using incompatible data formats; andif so, convert the message at the short message arbitrator from thefirst format to one of at least three different data formats.

Once the message is converted, the short message arbitrator can forwardthe message for receipt by the second device. The step of analyzingwhether the first device and the second device communicate useincompatible data formats may be performed by determining a mobileswitch center for the second device; determining a class of service forthe first device; determining a class of service for the second device;and determining a type of transport to use between the short messagearbitrator and the second device. By determining these features, theshort message arbitrator can properly prepare the message for deliveryby converting the incompatible data format into a format compatible withthe second device.

The above and other aspects of the system and method will be describedbelow in connection with the drawing set and the appended specificationand claim set.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an interconnect system according to anexemplary embodiment of the present invention.

FIG. 2 is a block diagram of an exemplary short message arbitrator ofthe system illustrated in FIG. 1.

FIG. 3 is a flow diagram illustrating an exemplary communications methodused by the CCL to transmit data to the remote locations.

FIG. 4 is a flow diagram illustrating an exemplary communications methodused by the remote locations to transmit data to the CCL.

FIG. 5 is a block diagram illustrating a prior art system forcommunication using a local carrier SMSC.

FIG. 6 is a block diagram illustrating a prior art system forcommunicating using a regional carrier SMSC.

FIG. 7 is a block diagram illustrating a prior art system forcommunicating where a home carrier has a direct roaming agreement with alocal carrier.

FIG. 8 is a block diagram illustrating a prior art system forcommunicating where a local carrier uses a clearing house SMSC forroaming data.

FIG. 9 is a block diagram illustrating a system for communicating usinga telemetry gateway according to an exemplary embodiment of the presentinvention.

FIG. 10A is a flow diagram illustrating an exemplary communicationsmethod for a message originating at a mobile radio.

FIG. 10B is a ladder diagram illustrating the sequence of communicationsfor a message originating at a mobile radio as described in FIG. 10Aaccording to an exemplary embodiment of the present invention.

FIG. 11A is a flow diagram illustrating an exemplary communicationsmethod for a message terminating at a mobile radio.

FIG. 11B is a ladder diagram illustrating the sequence of communicationsfor a message terminating at a mobile radio as described in FIG. 11Aaccording to an exemplary embodiment of the present invention.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

The present invention is directed to a system and method forcommunicating among digital cellular systems of multiple formats. Atelemetry gateway allows external messaging systems to send shortmessages to and receive short messages from multiple remote locationsusing different digital cellular or PCS standards. The telemetry gatewaycan convert inbound short messages from the typical communicationformats used in conventional wireless networks to a common telemetryprotocol for forwarding to external messaging service providers. Thetelemetry gateway can convert outbound short messages from the commontelemetry protocol to the format of the destination radio communicationdevice. The telemetry gateway also performs certain functions ofconventional SMSCs and HLRs to provide for faster and more efficientdelivery of short messages.

The present invention can be implemented in a variety of differentembodiments. The first exemplary embodiment described herein uses ashort message arbitrator (“SMA”) to intercept, convert, and transmitmessages of varying formats. The second exemplary embodiment describedherein uses the telemetry gateway which is capable of both convertingshort messages of different formats as well as transmitting andreceiving messages more quickly and efficiently than conventional SMSsystems.

Exemplary SMA Embodiment

FIG. 1 shows an exemplary system for providing a flexible bi-directionaldata transport between a CCL 100 and one or more remote locations usingwireless technologies. The CCL 100 sends and receives data to and fromremote locations 123, 124, 125 and 126. Data from the CCL 100 istransferred to the SMA 104 using a public voice/data transport 102 overdata circuits 101 and 103.

The SMA 104 converts the CCL's data to the proper format for transportto MSC's 109, 110, 117 and 119. The SMA 104 utilizes two routes fordelivering the CCL's data to MSC's 109, 110, 117, and 119. The SMA 104routes the CCL's data to one of the MSC's 109, 110, 117, and 119 by: 1)using a data circuit 105 to an SS7/IS41 Network 106, then over a datacircuit (107, 108, 115 or 116) to the MSC (109, 110, 117, or 119) thatis intended to receive the transmitted data; or 2) using a data circuit103 back to the public voice/data transport 102, then over a datacircuit (111, 112, 118, or 120) to the MSC (109, 110, 117, or 119) thatis intended to receive the transmitted data.

Depending on the wireless access method used at the remote location, theCCL's data is routed to the selected wireless market. For advancedmobile phone service (AMPS) wireless communications, the data istransported from the MSC 109 to an AMPS radio 113 and finally to theremote location 123. For time division multiple access (TDMA) wirelesscommunications, the data is transported from the MSC 117 to a TDMA radio121 and finally to the remote location 125. For code division multipleaccess (CDMA) wireless communications, the data is transported from theMSC 119 to a CDMA radio 122 and finally to the remote location 126. Forglobal system for mobile telecommunications (GSM), the data istransported from the MSC 110 to a GSM radio 114 and finally to theremote location 124.

The system of FIG. 1 provides for the bi-directional transport of databetween a CCL 100 and its remote locations (123, 124, 125, or 126) usinga wireless link (Cellular or PCS). The CCL 100 can use one or moremethods to deliver data to the SMA 104. The various methods employ avariety of communication system is components. Below are four examples:

1) a dial-up data connection via a voice circuit 101 to the publicvoice/data transport 102 (public switched telephone network), then overthe voice circuit 103;

2) a dial-up or dedicated data circuit 101 to the public voice/datatransport 102 (Internet) then over the data circuit 103;

3) a dedicated data circuit 101 to public voice/data transport 102(frame-relay private network) then over the data circuit 103; and

4) an ISDN circuit 101 to public voice/data transport 102 (publicswitched telephone network), then over the ISDN circuit 103.

After the SMA 104 receives the data from the CCL 100, it uses anidentifying characteristic, such as the mobile identification number(MIN) or international mobile station identifier (IMSI), that wasreceived with the data, to retrieve the CCL's profile 130 from a SMAdatabase 128. The SMA determines the following from the CCL profile: 1)the MSC (109, 110, 117, or 119) serving the remote radio (113, 114, 121or 122); 2) the wireless access method used in the MSC's market; 3) theCCL's class of service; and 4) the type of transport to use between theSMA 104 and the selected MSC (109, 110, 117, or 119). Based upon theinformation retrieved from the database, the SMA determines whether anyalterations are required to the data or identifying characteristic tomake the data compatible with a technologically dissimilar receivingunit or system.

The CCL's class of service may include one of the following:“CELLEMETRY” data service; short message system (SMS); asynchronousdigital data; or data over circuit switched voice cellular. “CELLEMETRY”data service is available to AMPS (analog and digital) radios, SMS andasynchronous digital data are available to digital radios (CDMA, GSM andTDMA), and circuit switched voice cellular is available in all methodsof wireless access. In addition, those skilled in the art willappreciate that other classes of service may be used with the CCL 100 ofthe present invention.

For simplicity only one CCL 100 is illustrated in FIG. 1. However, theSMA can support multiple CCL's. Each CCL served by the SMA has a CCLidentifier that is stored in the database.

FIG. 2 shows an exemplary SMA 104 of the present invention. Thecontroller 201 manages communication over the data circuits 103 and 105.The SMA database 128 (FIG. 1) stores a profile for each CCL 100supported by the SMA 104. The profile provides information to supportthe conversion and transport of data between a central location, such asCCL 100, and its remote locations, such as remote locations 123, 124,125, and 126. From the stored profiles the SMA determines the recipientof the communication, as well as the method of data transport and anydata conversions that are necessary.

The SMA analyzes the information about the CCL and the remote devicestored in the database to determine whether the CCL and the remote areusing compatible or incompatible data formats. If the CCL and the remoteare using incompatible data formats, then the SMA converts the data. Aswill be apparent to one skilled in the art, the conversion from one dataformat into another can be managed in any suitable way, e.g., throughmultiple bi-directional translators 205.

Exemplary Communication Methods with the SMA

FIGS. 3 and 4 are flow diagrams illustrating exemplary communicationmethods of the present invention. These figures illustrate thecommunication methods utilized to transfer data between the customercentral location (CCL) 100 and the remote locations (123, 124, 125, and126) of FIG. 1. The communication methods of FIGS. 3 and 4 allow theremote locations (123, 124, 125, and 126) and CCL 100 to communicate,even though they are connected by multiple wireless (e.g. digitalcellular and PCS) systems using multiple, otherwise incompatibleprotocols or data formats. In discussing the following flow diagrams,reference will be made to the elements of FIG. 1.

FIG. 3 is a flow diagram illustrating the communications method 300 usedby the CCL 100 to transfer data to a remote location (123, 124, 125, or126). Communications method 300 begins at step 302 and proceeds to step304. At step 304, the CCL 100 transports the data to SMA 104. The SMA104 at step 306 receives the data and retrieves the MIN, or otheridentifying characteristic, transported with the data. At step 308, theSMA 104 uses the MIN to retrieve the CCL's profile 130 from the SMAdatabase 128.

From the profile 130, the SMA 104 determines the MSC (109, 110, 117, or119) that is serving the remote radio (113, 114, 121 or 122) identifiedby the MIN, the wireless access method or data format used in the MSC'smarket, the class of service or data format used by the CCL, and themethod of transport to use between the SMA 104 and the selected MSC(109, 110, 117, or 119), in step 310. In step 311, the SMA determineswhether the data formats used by the CCL and the remote are compatible.If the data formats are compatible, then the Yes branch is followed tostep 313. However, if the data formats are not compatible, then the Nobranch is followed to step 312. At step 312, the SMA 104 converts thedata to the proper format.

At step 313, the SMA transports the data to the appropriate MSC (109,110, 117, or 119) using the method of transport specified in thedatabase. Proceeding to step 314, the MSC (109, 110, 117, or 119)receives and transports the data to the radio (113, 114, 121, or 122)associated with the remote location (123, 124, 125, or 126).Communications method 300 then proceeds to step 316. At step 316, theradio (113, 114, 121, or 122) receives the converted data and transportsit to the remote location (123, 124, 125, or 126). Finally,communications method 300 proceeds to step 318 and the method ends.

FIG. 4 is a flow diagram illustrating an exemplary remote communicationsmethod 400 used by the remote locations (123, 124, 125, or 126) totransfer data to the CCL 100. The remote communications method 400illustrates the steps used by a remote location (123, 124, 125, or 126)to transport data to the CCL 100. Remote communications method 400begins at step 402 and proceeds to step 404. At step 404, the remotelocation (123, 124, 125, or 126) commands its radio (113, 114, 121, or122) to send data to its associated MSC (109, 110, 117, or 119). At step406, the MSC (109, 110, 117, or 119) receives the data and transports itto the SMA 104.

The remote communications method 400 then proceeds to step 408. At step408, the SMA 104 receives the data and retrieves the identifyingcharacteristics, such as the MIN (or IMSI) and MSC identifier (MSCID),from the data. The SMA 104 searches the SMA database 128 using the MINand MSCID that the MSC (109, 110, 117 or 119) transported with the data.Next, at step 410, the SMA 104 determines from the SMA database 128: 1)the CCL identifier; 2) the class of service used by the identified CCL100; and 3) the wireless access method used by the MSC.

The SMA compares the class of service used by the CCL and the wirelessaccess method used by the MSC to determine whether the data formats arecompatible in step 411. If the data formats are compatible, then the Yesbranch is followed to step 413. However, if the data formats areincompatible, then the No branch is followed to step 412 and the data isconverted. Once the data is converted, the method proceeds to step 413.In step 413, the SMA delivers the data to the CCL. The SMA delivers thedata to the CCL using a transmission path that is appropriate for theCCL identified by the CCL identifier. Then, remote communications method400 proceeds to step 414 and ends.

Exemplary Communications with the SMA

The following examples are exemplary communications supported by thepresent invention. These examples are intended to illustrate some of thepossible communication schemes, between the CCL 100 and the remotelocations (123, 124, 125, and 126), that may be implemented with thepresent invention. These examples are in no way intended to limit thescope of the invention. Those skilled in the art will appreciate thatthere are many other possible schemes and protocols that may beimplemented with the present invention.

In a first example, the CCL 100 sends data to the remote location 123.The remote location 123 is associated with an AMP's radio 113 and theAMP's radio is served by MSC 109. The CCL's class of service is“CELLEMETRY” Data Service. The CCL 100 sends the MIN of the AMPS radio113 along with the data to be transported to the SMA 104. The SMA 104determines from the SMA database 128 that the MIN corresponds to theAMP's radio 113; the class of service is “CELLEMETRY” Data Service; andthe MSC 109 serves the radio 113.

Depending on the type of mobile switching center, either an IS41inter-system page message is sent from the SMA 104 to the MSC 109through data circuit 105, the SS7/IS41 network 106 and the data circuit108; or a roamer-access call is made from the SMA 104 to the MSC 109through circuit 103, public voice/data transport 102 and the datacircuit 111. The SMA determines the appropriate method of transportbetween the SMA 104 and the MSC 109 from the database 128. The MSC 109then broadcasts a page order, which is received by the AMPS radio 113and delivered to the remote location 123 to complete the transaction.

In another example, the remote location 123 sends data to the CCL 100.The remote location 123 is associated with the AMP's radio 113 and theAMP's radio is served by MSC 109. The remote location 123 sends amessage to the CCL 100 by commanding the AMPS radio 113 to generate aregeneration notification that is received by the MSC 109. The MSC 109then forwards the regeneration notification to the SMA 104, via the datacircuit 108, the SS7/IS41 network 106 and the data circuit 105. Once theSMA 104 receives the notification, the SMA 104 searches the SMA database128, using the MIN and the MSCID provided by the MSC 109. From thedatabase 128, the SMA 104 determines the following: 1) the CCLidentifier for the intended recipient; 2) the class of service used bythe CCL; and 3) and the wireless access method used by MSC 109. The SMA104 compares the class of service used by the CCL 100 and the wirelessaccess method used by MSC 109 to determine whether the data needs to beconverted. If so, the SMA 104 converts the data. The data is deliveredto the CCL 100 using the data circuit 103, public voice/data transport102 and the data circuit 101.

In a further example, the CCL 100 sends data to the remote location 125.The remote location 125 is associated with a TDMA radio 121 and the TDMAradio is served by MSC 117. The CCL 100 sends the MIN of the TDMA radio121 along with the data to the SMA 104. The SMA 104 determines from theSMA database 128 that the MIN corresponds to the TDMA radio 121; shortmessage system (SMS) is the class of service; the MSC 117 serves theradio 121, and the method of transport between the SMA and the MSC 117.In this example, the method of transport is via data circuit 105 andSS7/IS41 network 106. Once this information is retrieved, the SMA 104sends an IS41 SMS message to the MSC 117 through data circuit 105, theSS7/IS41 network 106, and data circuit 116. Then, MSC 117 sends a SMSmessage to radio 121, which in turn delivers the data to remote location125 to complete the transaction.

In a further example, the remote location 125 sends data to the CCL 100.The remote location 125 is associated with the TDMA radio 121 and theTDMA radio is served by MSC 117. The remote location 125 commands theTDMA radio 121 to originate an SMS message, which is received by the MSC117 and transported to the SMA 104. The SMS message is transported tothe SMA 104 through circuit 116, the SS7/IS41 network 106 and, the datacircuit 105. The SMA 104 then searches the SMA database, using the MINand the MSCID provided by the MSC 117, and determines: the CCLidentifier; the class of service used by the CCL identified by the CCLidentifier; and the wireless access method used by the MSC 117. The SMA104 compares the class of service used by the CCL 100 and the wirelessaccess method used by the MSC 117 to determine whether the data needs tobe converted. If so, the SMA 104 converts the data. The data is thendelivered to the CCL 100 using the data circuit 103, the publicvoice/data transport 102 and the data circuit 101.

In yet a further example, the CCL 100 wishes to send data to the remotelocation 126. The remote location 126 is associated with a CDMA radio122 and the CDMA radio is served by MSC 119. The CCL 100 sends the MINof the CDMA radio 122 along with the data to be transported to the SMA104. The SMA 104 determines from the SMA database 128 that the MINcorresponds to the CDMA radio 122; asynchronous digital data is theclass of service; that the MSC 119 serves the CDMA radio 122; and thatthe method of transport from the SMA 104 to the MSC 119 is via datacircuit 103 and public voice/data transport 102. Once this informationis retrieved, a data message is sent from the SMA 104 to MSC 119. Themessage is sent through data circuit 103, public voice/data transport102, and the data circuit 120. The data message is then sent by the MSC119 to the CDMA radio 122, which in turn sends the data message to theremote location 126 to complete the transaction.

In a final example, the remote location 126 wishes to send data to theCCL 100. The remote location 126 is associated with a CDMA radio 122 andthe CDMA radio is served by MSC 119. The remote location 126 requeststhat CDMA radio 122 initiate an asynchronous digital data call, which isreceived by the MSC 119 and transported to the SMA 104. The MSC 119transports the data call via the data circuit 120, the public voice/datatransport 102, and data circuit 103. The SMA 104 then searches the SMAdatabase 128, using the MIN and the MSCID provided by the MSC 119, anddetermines: the CCL identifier for the intended recipient; the class ofservice used by the intended recipient; and the wireless access methodused by the MSC 119. The SMA 104 compares the class of service used bythe CCL 100 and the wireless access method used by the MSC 119 todetermine whether the data needs to be converted. If so, the SMA 104converts the data. The data is then delivered to the CCL 100 using thedata circuit 103, the public voice/data transport 102 and the datacircuit 101.

While a preferred embodiment has been set forth above, those skilled inthe art who have reviewed the present disclosure will readily appreciatethat other embodiments can be realized within the scope of the presentinvention. For example, transmission between the CCL 100 and the SMA 104can take place through any suitable network, such as a TCP/IP Network.Also, any SMS protocol can be used.

Exemplary Telemetry Gateway Embodiment

In an alternate embodiment, the present invention can be implementedusing a telemetry gateway. A telemetry gateway comprises hardware andsoftware modules capable of communicating messages to MSCs in variousdigital networks. The telemetry gateway can perform certain functions ofan HLR and SMSC found in conventional SMS systems, as illustrated inFIGS. 5-8. Replacing the HLR and the SMSC used in conventional SMSsystems allows the telemetry gateway to provide faster and moreefficient routing of messages. Specifically, instead of the “store andforward” functions performed by the SMSC that typically cause a lag ofminutes or hours in the transmission of messages, the telemetry gatewaydoes not store the messages it receives. The telemetry gateway typicallyprocesses and transmits messages in milliseconds. The telemetry gatewayis more efficient than conventional SMS systems because it considers allmessages as roaming and eliminates the need to query the HLR beforesending a message to a mobile communication device. The telemetrygateway offers a further advantage over a conventional SMSC in that italso has the ability to convert messages having different messagingprotocols.

Referring to FIG. 9, an exemplary architecture 900 is illustrated forimplementing an SMS telemetry gateway 930. In the exemplary architecture900, the SMS telemetry gateway 930 can communicate with digital networksusing a variety of different wireless access formats. While exemplaryarchitecture 900 illustrates a TDMA network, a CDMA network, and a GSMnetwork, those skilled in the art will understand that the invention isnot limited to these examples of digital networks. Similarly, while theSMS telemetry gateway 930 is shown coupled to a telemetry serviceprovider 935, the present invention is not limited to a single serviceprovider. The SMS telemetry gateway can communicate with serviceproviders supporting a variety of external messaging systems includingemail, voicemail, paging, and Web-based messaging.

Turning to the general digital network 910, a cellular mobileradiotelephone, or radio, 905 can transmit a message via the network 910to the MSC, or serving switch, 915. The radio 905 may be a fixed ormobile radio communication device. The serving switch 915 determinesthat the message is a roaming communication and transmits the message tosignal transfer point 920 for routing to the SMS telemetry gateway 930via SS7 network 925. Although the SS7 network 925 is the method fortransmission to the SMS telemetry gateway 930 in the preferredembodiment illustrated in FIG. 9, other data networks can also performthe same function. Upon receipt of the message, the SMS telemetrygateway 930 converts the message to a common telemetry protocol anddetermines the destination service provider 935 from the message'saddress field. The SMS telemetry gateway 930 can also conform theconverted message to any delivery preferences for the service provider935 stored in database 933. For example, an alternate network addressfor the service provider 935 may be stored in database 933.

Once the delivery preferences are conformed, the SMS telemetry gateway930 transmits the message in the common protocol to the appropriateservice provider 935. In contrast to the SMSC of conventional SMSsystems, the SMS telemetry gateway 930 does not store the message forlater delivery. Instead, the SMS telemetry gateway 930 transmits themessage to the service provider 935 as soon as the processing steps arecompleted. The SMS telemetry gateway typically processes and transmitsmessages in a few milliseconds as opposed to the minutes or hours ofdelay with conventional SMS systems.

When the service provider 935 receives the telemetry message, it canpackage the message for its subscribers in a variety of formats. Forexample, the service provider 935 can insert the message into an emailfor delivery to an email system. In another embodiment, the serviceprovider 935 can use the message to create a voicemail which isforwarded to the subscriber. The service provider 935 can also transmita confirmation that the message was received to the SMS telemetrygateway 930.

The SMS telemetry gateway 930 is a bidirectional system that can alsotransmit messages from the service provider 935 to radio 905. When theSMS telemetry gateway 930 receives a message from the service provider935, it requests routing information from the switch 915 at thedestination network 910. The SMS telemetry gateway 930 converts themessage to the wireless access format used at the destination network910 and transmits the message.

The SMS telemetry gateway's 930 direct access to the SS7 network 925, asillustrated in exemplary architecture 900, allows for faster and moreefficient communication of short messages. Furthermore, its ability toconvert messages from a variety of different wireless access formatsenables communication with a greater number of networks.

Exemplary Communication Methods with the Telemetry Gateway

FIGS. 10A and 11A illustrate exemplary methods for communicatingmessages using the SMS telemetry gateway 930 in accordance with anexemplary embodiment of the present invention. FIG. 10A illustrates anexemplary communication method for a message originating at a mobileradio, whereas FIG. 11A is an example of a method for a mobile radioterminating message. Those skilled in the art will recognize that themethods illustrated in FIGS. 10A and 11A are only examples and thatother messaging techniques can be implemented in other embodiments usingthe SMS telemetry gateway.

Referring to FIG. 10A, exemplary method 1000 is illustrated fortransmitting a message originating at a mobile radio. The sequence ofsteps performed in exemplary method 1000 are also shown in exemplaryladder diagram 1080 illustrated in FIG. 10B. Referring to exemplarymethod 1000, the switch 915 receives a message, or “SM”, from the radio905 in step 1005. The switch queries its visitor location register(“VLR”) in step 1010 to locate a profile for the radio 905. The VLR is adatabase comprising temporary information about subscribers of onenetwork that are roaming into another network. The switch uses theinformation in the VLR to complete roaming communications.

If there is no entry in the VLR database in step 1015, the switch 915sends a registration notification to the telemetry gateway 930 to obtainaccount and service information for the subscriber. The switch 915receives the registration response with the needed information from theSMS telemetry gateway 930 in step 1025 and creates a profile in the VLRdatabase in step 1030. The terms “registration notification” and“registration response” are used herein to refer to general steps foridentifying the radio communications device. These terms do not limitthe invention to particular types of networks or protocols.

Alternatively, if a VLR entry already exists in step 1015, the switch915 can proceed directly to step 1035 and transmit the message to thesignal transfer point 920 for routing to the SMS telemetry gateway 930in step 1040. A characteristic of SMS communications includes guaranteeddelivery of messages through the use of confirmation messages. Forexample, when the SMS telemetry gateway 930 receives the message, itreturns a confirmation response to the switch 915 in step 1045. In step1050, the SMS telemetry gateway converts the received message from theprotocol used at the originating network 910 to the common telemetryprotocol used by the service provider 935.

In steps 1055 and 1060 of exemplary method 1000, the SMS telemetrygateway uses the originating address field to determine the routing tothe service provider 935 and to check for any delivery preferencesstored in database 933. The converted message is ready for delivery tothe service provider 935 in step 1065. Upon delivery, the serviceprovider 935 typically transmits a delivery confirmation response to theSMS telemetry gateway. The SMS telemetry gateway 930 performs steps1050-1065 in a matter of milliseconds, which is a significantimprovement over the conventional “store and forward” techniques of theSMSC platforms used in SMS systems.

Turning to FIG. 11A, an exemplary method 1100 is illustrated fortransmitting a message that originates at a service provider andterminates at a mobile radio. Exemplary ladder diagram 1180 shown inFIG. 11B also illustrates the sequence of steps described in exemplaryprocess 1100. Process 1100 begins with the service provider 935transmitting a message, or SM, to the SMS telemetry gateway 930 in step1105. The service provider 935 receives the message from a subscriberusing one of the messaging systems that the service provider 935supports such as an email or paging system. In steps 1110 and 1115, theSMS telemetry gateway 930 sends an acknowledgment to the serviceprovider 935 and requests routing information for the message from theswitch 915 in the destination network. If there is a VLR entry for theSMS telemetry gateway in step 1120, the switch will proceed withproviding the routing information in step 1135.

However, if the switch 915 does not recognize the radio 905, the switchwill need to create a VLR entry in its database. The switch 915 createsa VLR entry in steps 1125 and 1130 by sending a qualification requestfor account and service information to the SMS telemetry gateway 930.Once the switch 915 creates a VLR entry, it can provide the routinginformation for the SMS telemetry gateway 930 in step 1135.

The wireless access format that the destination network employs istypically stored in a database at the SMS telemetry gateway 930. The SMStelemetry gateway 930 uses the format information to convert themessage, in step 1140, to the format expected at the destinationnetwork. In steps 1145 and 1150, the SMS telemetry gateway 930 transmitsthe converted message to the switch 915 and the switch 915 forwards themessage to the radio 905. Consistent with the guaranteed delivery of theSMS system, the switch 915 returns an acknowledgment of delivery in step1155 and the SMS telemetry gateway 930 forwards an acknowledgment to theservice provider 935 in step 1160.

In conclusion, the present invention, as represented in the foregoingexemplary embodiments, provides a system and method for communicatingshort messages that is more flexible and efficient than conventional SMSsystems. The exemplary SMS telemetry gateway can convert messages todifferent message formats in order to support communication with avariety of wireless networks. The exemplary SMS telemetry gateway alsoperforms the routing functions of components in conventional SMSsystems, but does so more quickly and efficiently.

It will be appreciated that the present invention fulfills the needs ofthe prior art described herein and meets the above-stated objects. Whilethere has been shown and described the preferred embodiment of theinvention, it will be evident to those skilled in the art that variousmodifications and changes may be made thereto without departing from thespirit and the scope of the invention as set forth in the appendedclaims and equivalents thereof. For instance, the present inventioncould be implemented in data networks other than the SS7 networkillustrated in exemplary architecture 900. The invention can also beadapted to support communication with messaging protocols other than thewireless access formats described herein.

1. A communication method, comprising the steps of: receiving a messageat a telemetry gateway; converting the message at the telemetry gatewayfrom a first format to one of at least three different formats such thatdata content of the message can be received by a recipient; andresponsive to conversion of the message, transmitting the convertedmessage from the telemetry gateway to the recipient without completing astore and forward process.
 2. The method of claim 1, further comprisingthe steps of: receiving at the telemetry gateway a registrationnotification from a mobile switching center; and sending from thetelemetry gateway a registration response to the mobile switchingcenter, the registration response comprising information concerning therecipient.
 3. The method of claim 1, wherein the first format comprisesone of CDMA, TDMA, and GSM.
 4. The method of claim 1, wherein one of theat least three different formats comprises a format compatible with oneof an email system, a voicemail system, or a web-based messaging system.5. The method of claim 1, further comprising the step of sending anacknowledgment from the telemetry gateway to an originator of themessage confirming that the message has been delivered to the recipient.6. The method of claim 1, wherein the telemetry gateway receives themessage from a signal transfer point.
 7. A method for routing a messageusing a telemetry gateway, comprising the steps of: receiving at thetelemetry gateway the message from a communication device; requesting bythe telemetry gateway routing information from a mobile switchingcenter; receiving at the telemetry gateway the routing information;based on the routing information, converting the message at thetelemetry gateway from a first format to one of at least three differentformats; and responsive to conversion of the message, transmitting theconverted message from the telemetry gateway to the mobile switchingcenter without completing a store and forward process.
 8. The method ofclaim 7, further comprising the steps of: when the mobile switchingcenter does not have a database entry for the recipient, receiving atthe telemetry gateway a qualification request from the mobile switchingcenter; and sending by the telemetry gateway a qualification response tothe mobile switching center.
 9. The method of claim 7, furthercomprising the step of sending an acknowledgement from the telemetrygateway to the communication device confirming delivery of the messageto the recipient.
 10. A telemetry gateway, coupled to a data source,having a software module stored in a memory storage device, the softwaremodule comprising computer-readable instructions that, when executed,implement the steps of: determining the destination of a messagereceived from a first communication device based on data containedwithin the message; converting the message from a first format to one ofat least three different formats; and forwarding the message fordelivery to a second communication device in one of the at least threedifferent formats without completing a store and forward process. 11.The telemetry gateway of claim 10, wherein the telemetry gateway isfurther connected to a SS7 data inter-networking system.
 12. Thetelemetry gateway of claim 11, wherein the message is forwarded from thetelemetry gateway to the second communication device using the SS7 datainter-networking system.
 13. The telemetry gateway of claim 10, whereinthe message passes through a mobile switching center before beingreceived by the telemetry gateway.
 14. The telemetry gateway of claim10, wherein the software module is further configured to: send a routerequest to a mobile switching center; and receive route information fromthe mobile switching center.
 15. The telemetry gateway of claim 10,wherein the software module is further configured to: receive aregistration notification from a mobile switching center; send aregistration response to the mobile switching center, wherein theregistration response contains account and service information relatedto one of the communication devices.
 16. The telemetry gateway of claim10, wherein the first format is converted from a wireless access formatto a format compatible with one of an email system, a voicemail system,or a web-based messaging system.
 17. The telemetry gateway of claim 10,wherein the first format is converted from a format compatible with oneof an email system, a voicemail system, or a web-based messaging systemto a wireless access format.
 18. A method for routing a message betweena first device and a second device, comprising the steps of: receiving amessage having a first data format at a short message arbitrator;accessing a database at the short message arbitrator containing aprofile for the first device and the second device; based on theprofile, analyzing at the short message arbitrator whether the firstdevice and second device communicate using incompatible data formats;and converting the message at the short message arbitrator from thefirst format to one of at least three different data formats; andforwarding the message by the short message arbitrator in the convertedformat for receipt by the second device.
 19. The method of claim 18,wherein the step of analyzing whether the first device and second devicecommunicate using incompatible data formats comprises: determining amobile switching center for the second device; determining a class ofservice for the first device; determining a class of service for thesecond device; and determining a type of transport to use between theshort message arbitrator and the second device.
 20. The method of claim19, wherein the class of service for the first device comprises at leastone of short message system; asynchronous digital data; and data overcircuit switched voice cellular.
 21. The method of claim 19, wherein themobile switching center is determined based on a mobile identificationnumber associated with the second device.
 22. The method of claim 19,wherein the short message arbitrator forwards the message for receipt bythe second device based on the determined type of transport to usebetween the short message arbitrator and the second device.